-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Blocked] feat: adding more fields to vault scalar #77
Conversation
Do you guys have any thoughts on the assumptions I have made so far in this pr @nud3l @bvotteler :
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of smaller issues to get sorted, a few of those just formatting related.
And two other important bits:
- Please restore the
.env
file to what it was - You need to merge master in to resolve conflicts.
I suggest to regenerate the database migration files from scratch after merging master back in. Feel free to simply remove all migration files and regenerate a single one.
We will need to reindex from the start as we deploy the next version anyway.
We could also check in with the parachain devs whether we can get an event added for thresholds being set. That would save us from having to query state. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Leaving as comment only (instead of change requested), so I won't block approvals while I'm out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please restore this file so it doesn't mess with README instructions for quick starts.
Once these events are merged into the blockchain, I will be able complete this pr. |
Closing stale PR |
Pr for adding to vault scalar.